Method and apparatus for communicating over a long physical uplink channel resource

ABSTRACT

A semi-static configuration information for a short physical uplink channel resource corresponding to a short physical uplink channel can be received at a device. Scheduling information to transmit over a long physical uplink channel resource corresponding to a long physical uplink channel can be received. The long physical uplink channel resource and the short physical uplink channel resource can at least partially overlap in time. The long physical uplink channel can be longer in duration than the short physical uplink channel. The long physical uplink channel resource can be transmitted over if the device does not support an uplink transmission on one or more non-contiguous physical resource blocks in the frequency domain.

BACKGROUND 1. Field

The present disclosure is directed to a method and apparatus forcommunicating on a wireless network. More particularly, the presentdisclosure is directed to communicating using a physical uplink channelon a wireless wide area network.

2. Introduction

Presently, wireless communication devices, such as User Equipments(UEs), communicate with other communication devices using wirelesssignals. A Physical Uplink Control Channel (PUCCH) carries UplinkControl Information (UCI) such as Hybrid Automatic RepeatRequest-Acknowledgement (HARQ-ACK) feedback, Scheduling Requests (SR),and Channel State Information (CSI). In Fifth Generation (5G) RadioAccess Technology (RAT), such as 3rd Generation Partnership Project(3GPP) New Radio (NR) RAT, two types of PUCCH formats in terms oftransmission duration, short PUCCH and long PUCCH, can be defined tosupport various services requirements. Short PUCCH with 1 or 2Orthogonal Frequency Division Multiplexing (OFDM) or Discrete FourierTransform-spread-OFDM (DFT-s-OFDM) symbol duration is suitable forsupport of low-latency traffic with fast HARQ-ACK feedback. Long PUCCHhas 4-14 OFDM or DFT-S-OFDM symbols of a slot, where a slot can bedefined as a time unit that has one or more symbols. The long PUCCH alsomay span over multiple slots that can be used for coverage extensionand/or large payload UCI transmission.

During contention-based 4-step random access procedure, a Message 4(Msg4) is transmitted by a Network Entity (NE), such as a gNodeB (gNB),for contention resolution, and it may be addressed by either a CellRadio Network Temporary Identifier (C-RNTI) that is included in Msg 3from a UE, such as for the case of connected mode UEs, or a temporaryC-RNTI that is included in a Random Access Response (RAR) message, suchas Msg2, from the NE. The UE transmits Acknowledgement (ACK) if the UEcorrectly decodes Msg4 and detects its own identity. If the UE fails todecode Msg4, misses a Downlink (DL) grant, or correctly decodes Msg4 butdiscovers another UE's identity in the decoded Msg4, the UE does notsend anything, which is known as Discontinuous Transmission (DTX). Sincea valid dedicated PUCCH resource has not yet been configured for the UEduring the contention-based random access procedure due to initialaccess or due to Uplink (UL) timer expiration and release/reset ofpreviously configured PUCCH resources, a method to determine a PUCCHresource for HARQ-ACK feedback in response to Msg4 needs to bedeveloped.

To support Ultra-Low Latency (ULL) services with close-to-zeroscheduling delay, a UE may need to be configured with multiple shortPUCCH-based ULL SR resources within a slot. Further, with mini-slotbased scheduling, a short PUCCH or a short Physical Uplink SharedChannel (PUSCH) may occur on any symbol within a slot, instead of on thelast few symbols of the slot. When the UE has to concurrently serve twodifferent types of traffic, such as normal latency traffic and ULLtraffic, it is useful to define rules to multiplex slot-based long PUSCHand/or PUCCH, such as physical uplink channels, for normal latencytraffic with mini-slot based short PUCCH/PUSCH for ULL traffics.

As for HARQ-ACK feedback in response to Msg4, it has been proposed thata UE determines a PUCCH resource in an implicit or explicit manner, suchas indicated by DL scheduling Downlink Control Information (DCI), from aset of group-common or common PUCCH resources configured via a RAR or aSystem Information Block (SIB). Because of potential retransmission ofMsg3, delay for successful Msg3 transmission and reception may bedifferent for different UEs using the same Random Access Channel (RACH)time/frequency resource, and delay distribution may change over time.Thus, there may be the case that NE cannot confine a UEs' HARQ-ACKfeedback transmissions in response to Msg4 within a predefined set ofPUCCH resources, such as when all UEs transmitting RACH preambles in thesame RACH radio resource have similar or same delay for successful Msg3transmissions, unless the PUCCH resource set is over-provisioned. Theover-provisioned common PUCCH resource set would potentially degradespectral efficiency.

It has also been proposed to multiplex long PUCCH with short PUCCH inCode Division Multiplexing (CDM) manner when they are transmitted fromone UE in the same slot and when long PUCCH uses a PUCCH format withorthogonal code-based multi-user multiplexing. When a UE can use longPUCCH and short PUCCH as per channel conditions, such as path loss, longPUCCH is typically used for large payload UCI transmission. Since thePUCCH format with orthogonal code based multi-user multiplexing ismainly for small payload UCI transmission, CDM of long PUCCH with shortPUCCH from the same UE may not be a relevant use case.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which advantages and features of thedisclosure can be obtained, a description of the disclosure is renderedby reference to specific embodiments thereof which are illustrated inthe appended drawings. These drawings depict only example embodiments ofthe disclosure and are not therefore to be considered to be limiting ofits scope. The drawings may have been simplified for clarity and are notnecessarily drawn to scale.

FIG. 1 is an example block diagram of a system according to a possibleembodiment;

FIG. 2 is an example illustration of long PUCCH type selection forHARQ-ACK feedback to Msg4 based on the number of Msg3 transmissionsaccording to a possible embodiment;

FIG. 3 is an example illustration of short PUCCH type selection forHARQ-ACK feedback to Msg4 based on the number of Msg3 transmissionsaccording to a possible embodiment;

FIG. 4 is an example illustration of multiplexing semi-staticallyconfigured short PUCCH with slot-based PUSCH from different UEsaccording to a possible embodiment;

FIG. 5 is an example illustration of multiplexing semi-staticallyconfigured short PUCCH with slot-based PUSCH from one UE according to apossible embodiment;

FIG. 6 is an example illustration of a puncturing pattern for mini-slotlevel monitoring of puncturing DCI within a slot-based PUSCH accordingto a possible embodiment;

FIG. 7 is an example illustration of a puncturing pattern for slot levelmonitoring of puncturing DCI within a slot-based PUSCH according to apossible embodiment;

FIG. 8 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment;

FIG. 9 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment;

FIG. 10 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment;

FIG. 11 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment;

FIG. 12 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment;

FIG. 13 is an example flowchart illustrating the operation of a wirelesscommunication device according to a possible embodiment; and

FIG. 14 is an example block diagram of an apparatus according to apossible embodiment.

DETAILED DESCRIPTION

Some embodiments provide a method and apparatus for communicating on awireless network. Some embodiments can further provide a method andapparatus for transmitting and/or receiving a HARQ-ACK feedback on an ULcontrol channel Some embodiments can additionally provide a method andapparatus for transmitting and/or receiving over a long physical ULchannel resource. Some embodiments can also provide a method andapparatus for transmitting and/or receiving a physical UL channel basedon modification information.

According to a possible embodiment, a lack of a valid dedicated ULcontrol channel resource configuration can be ascertained by a device. Anumber of symbols for an UL control channel can be determined inresponse to ascertaining a lack of a valid dedicated UL control channelresource configuration. A DL message can be received. The DL message canbe based on a device identity of the device. A HARQ-ACK feedback can betransmitted on the UL control channel using the determined number ofsymbols in response to receiving the DL message.

According to another possible embodiment, a number of symbols for an ULcontrol channel can be determined by a device. System informationindicating the number of symbols for the UL control channel can betransmitted. A DL message based on a device identity can be transmitted.HARQ-ACK feedback can be received on the UL control channel using theindicated number of symbols in response to transmitting the DL message.

According to another possible embodiment, a semi-static configurationinformation for a short physical UL channel resource corresponding to ashort physical UL channel can be received at a device. Schedulinginformation to transmit over a long physical UL channel resourcecorresponding to a long physical UL channel can be received. The longphysical UL channel resource and the short physical UL channel resourcecan at least partially overlap in time. The long physical UL channel canbe longer in duration than the short physical UL channel. The longphysical UL channel resource can be transmitted over if the device doesnot support an UL transmission on one or more non-contiguous PRBs in thefrequency domain.

According to another possible embodiment, semi-static configurationinformation for a short physical UL channel resource corresponding to ashort physical UL channel can be ascertained by a device. Thesemi-static configuration information for the short physical UL channelresource can be transmitted. Scheduling information to transmit over along physical UL channel resource corresponding to a long physical ULchannel can be determined. The long physical UL channel and the shortphysical UL channel resource can at least partially overlap in time. Thelong physical UL channel can be longer in duration than the shortphysical UL channel. The determined scheduling information can betransmitted. Information can be received on the long physical UL channelresource.

According to another possible embodiment, scheduling information totransmit a physical UL channel can be received at a device. Thescheduling information can include modification information regardingmodifying a physical UL channel transmission. The physical UL channelcan be transmitted based on the scheduling information including themodification information.

According to another possible embodiment, scheduling information totransmit a physical UL channel can be determined by a device. Thescheduling information can include modification information regardingmodifying a physical UL channel transmission. The scheduling informationincluding the modification information can be transmitted. The physicalUL channel based on the scheduling information including themodification information can be received.

FIG. 1 is an example block diagram of a system 100 according to apossible embodiment. The system 100 can include a User Equipment (UE)110, at least one Network Entity (NE) 120 and 125, such as a basestation, and a network 130. The UE 110 can be a wireless wide areanetwork device, a user device, wireless terminal, a portable wirelesscommunication device, a smartphone, a cellular telephone, a flip phone,a personal digital assistant, a personal computer, a selective callreceiver, an Internet of Things (IoT) device, a tablet computer, alaptop computer, or any other user device that is capable of sending andreceiving communication signals on a wireless network. The at least oneNE 120 and 125 can be wireless wide area network base stations, can beNodeBs, can be enhanced NodeBs (eNBs), can be New Radio (NR) NodeBs(gNBs), such as 5G NodeBs, can be unlicensed network base stations, canbe access points, can be base station controllers, can be networkcontrollers, can be Transmission/Reception Points (TRPs), can bedifferent types of base stations from each other, and/or can be anyother network entities that can provide wireless access between a UE anda network.

The network 130 can include any type of network that is capable ofsending and receiving wireless communication signals. For example, thenetwork 130 can include a wireless communication network, a cellulartelephone network, a Time Division Multiple Access (TDMA)-based network,a Code Division Multiple Access (CDMA)-based network, an OrthogonalFrequency Division Multiple Access (OFDMA)-based network, a Long TermEvolution (LTE) network, a NR network, a 3GPP-based network, a satellitecommunications network, a high altitude platform network, the Internet,and/or other communications networks.

In operation, the UE 110 can communicate with the network 130 via atleast one network entity 120. For example, the UE can send and receivecontrol signals on a control channel and user data signals on a datachannel.

Some embodiments can provide resource allocation and multiplexing forflexible uplink communications. Some embodiments can additionallyprovide a HARQ-ACK resource for Msg4 during RACH procedure. Someembodiments can also provide methods to determine a PUCCH resource forHARQ-ACK feedback in response to Msg4. Some embodiments can furtherprovide methods to multiplex slot-based long PUSCH/PUCCH with mini-slotbased short PUCCH/PUSCH.

According to a possible embodiment, a UE can always employ a long PUCCHfor HARQ-ACK feedback to Msg4 to avoid potential PUCCH coveragelimitation and UE capability issues. During initial access, it may bedifficult for a NE to estimate UL path loss, a UE's power headroom, orUE capability to support low latency traffic with short PUCCH/PUSCH.Thus, the long PUCCH with longer transmission duration may guaranteereliable UCI decoding and serve all types of UEs. In one example, thelong PUCCH for HARQ-ACK feedback to Msg4 may consist of or include apre-determined number of OFDM or DFT-s-OFDM symbols based on thereference numerology of a given frequency band. Pre-determined longPUCCH duration can be easily accommodated in Frequency DivisionDuplexing (FDD) systems, as the number of available UL symbols does notchange over slots. In another example, a NE can indicate, as a part ofsystem information, the number of symbols for the long PUCCH carryingHARQ-ACK feedback for Msg4, which may depend on a cell size and/or thenumber of semi-statically configured symbols for a downlink controlregion for particularly a TDD system. Alternatively, the NE canimplicitly or explicitly indicate the number of symbols for the longPUCCH carrying HARQ-ACK feedback for Msg4 in the DCI that includes DLscheduling information for Msg4. One example of implicit indication isthat the NE can indicate a starting and/or ending symbol(s) of the longPUCCH. Further, the duration of long PUCCH, such as single-slot ormulti-slot long PUCCH, can be determined according to the total numberof PUSCH transmissions required for successful Msg3 decoding.Additionally, or alternatively, the duration of long PUCCH can bedetermined according to the available UL symbols in a slot whereHARQ-ACK feedback to Msg4 will be transmitted. In another example, theduration of long PUCCH may be determined based on the Modulation andCoding Scheme (MCS) of the Msg3 PUSCH transmission. The duration of longPUCCH may be based on one or more of the above schemes. In one example,the duration of long PUCCH may be a separately encoded field of the DCIor may be jointly encoded with other msg4 DCI information in the DCI.

In one example, a UE that knows its UE identity, such as Cell RadioNetwork Temporary Identifier (C-RNTI) is unknown to the NE, such as whenthe UE is not in a Radio Resource Control (RRC)-connected state, can uselong PUCCH for HARQ-ACK feedback to Msg4. If a UE knows its UE identity,such as C-RNTI, is known to the NE, such as when the UE is in anRRC-connected state, the UE can use long PUCCH or short PUCCH for msg 4HARQ-ACK feedback based on one or more of short PUCCH UE capability, aPUCCH type and/or duration configuration signaling, a short PUCCH ifpath loss less than a threshold, a number of PUSCH transmissionsrequired for successful Msg3 decoding, MCS allocated to Msg 3, and/orother criteria described in this disclosure.

According to another possible embodiment, a NE may determine andindicate a PUCCH type in terms of time duration, such as short or long,for UE's HARQ-ACK feedback to Msg4, based on preamble received power,the total number of PUSCH transmissions required for successful Msg3decoding, and/or an implicit indication from the UE. Alternatively, boththe NE and the UE may identify the PUCCH duration type for HARQ-ACKfeedback to Msg4 based on the total number of Msg3 transmissions. The UEmay interpret some of DCI bit fields in a PDCCH that delivers schedulinginformation for Msg4 and the UE's HARQ-ACK feedback to Msg4 differentlydepending on the identified PUCCH duration type. If the UE is capable ofsupporting a short PUCCH, the UE can indicate in Msg3 whether to supportshort PUCCH or not, such as via a 1-bit flag. In one example, if onlyone Msg3 transmission occurs before Msg4 reception, the UE can use ashort PUCCH for HARQ-ACK feedback to Msg4.

Otherwise, the UE can use a long PUCCH for HARQ-ACK feedback to Msg4. Inanother example, the NE can partition a set of preambles into two ormore subsets and the UE can select a preamble subset depending on a DLpath loss estimate. DL path loss threshold value(s) for each preamblesubset can be predefined or can be signaled as a part of RACHconfiguration information. If the NE detects a preamble from thepreamble subset corresponding to DL path loss larger than a certainvalue and/or schedules one or more retransmission(s) of Msg3, the NE caninform the UE to use a long PUCCH via DCI that includes DL schedulinginformation for Msg4. Further, the NE can transmit a dynamic indicationon the number of symbols for the long PUCCH.

Considering that HARQ-ACK feedback to Msg4 is either ACK or DTX, similarto SR on/off signaling, one sequence can be allocated for Msg4 HARQ-ACKfeedback to indicate ACK or DTX. Furthermore, a HARQ-ACK PUCCH inresponse to Msg4 can be code-division multiplexed (CDM'ed) withsequence-based SR PUCCHs from other UEs or sequence-based HARQ-ACKPUCCHs from other UEs.

In order to avoid radio resource waste or PUCCH resource blocking frompre-configured common PUCCH resources, DL scheduling DCI for Msg4 caninclude information on allocated Physical Resource Blocks (PRBs) andallocated sequences, such as cyclic shifts of a base sequence, forHARQ-ACK transmission with limited signaling overhead. In one example,for long PUCCH, an allocated PRB index, where PRB indexing starts from abandwidth part boundary, can be determined based on a dynamicallysignaled value together with a semi-statically indicated, such as viaRAR or SIB, PRB offset. In another example, for short PUCCH, DCI canindicate a sub-band group index and allocated PRB(s) within the assignedsub-band group, where the sub-band group includes one or more contiguousor non-contiguous sub-bands and a sub-band includes one or moreconsecutive PRBs. The aforementioned methods for UE's HARQ-ACK feedbackto Msg4 are also applicable to PUCCH resource determination for UE'sHARQ-ACK transmission when UE does not have dedicated PUCCH resourceconfiguration.

FIG. 2 is an example illustration 200 of long PUCCH type selection forHARQ-ACK feedback to Msg4 based on the number of Msg3 transmissionsaccording to a possible embodiment. FIG. 3 is an example illustration300 of short PUCCH type selection for HARQ-ACK feedback to Msg4 based onthe number of Msg3 transmissions according to a possible embodiment.After a UE's RRC connection establishment, a NE can determine or switcha PUCCH type between long PUCCH and short PUCCH for the UE's subsequentUCI transmission based on at least the UE's Power Headroom Report (PHR)and/or the average number of UL transmissions for successful decoding ofone UL Transport Block (TB) during a certain period. If the UE has powerheadroom smaller than a certain threshold, the NE can indicate the UE touse long PUCCH in order to overcome a potential UL transmit powerlimitation. A high number of retransmissions may occur if theinterference level changes dynamically and accordingly, the initialselection of MCS may not be optimal. In this case, overprovisioningPUCCH resources by using long PUCCH may be useful to avoid potentialPUCCH decoding error due to dynamic interference variation.

According to a possible implementation, slot-based long PUSCH/PUCCH andmini-slot based short PUSCH/PUCCH can coexist. UEs that are not limitedby uplink Transmit (Tx) power or have sufficient power headroom, such asabove a certain threshold, may be able to use both long PUCCH and shortPUCCH depending on UCI types, traffic types, and/or applications. Forexample, a UE may be semi-statically configured with a long PUCCHresource for periodic transmission of large payload UCI, such as aperiodic CSI report including narrow beam related information, while ashort PUCCH resource can be used for SR or HARQ-ACK transmission. Inanother example, mini-slot based short PUSCH/PUCCH can be used forUltra-Reliable Ultra-Low-Latency (URLLC) traffic, and slot-based longPUSCH/PUCCH can be employed for normal traffic, such as regular latencytraffic.

When multiplexing slot-based and mini-slot based uplink transmissionswithin a UE, potential issues on inter-modulation and Power Amplifier(PA) output power back-off can be taken into account. For example,simultaneous transmission of long PUSCH/PUCCH and short PUSCH/PUCCH fromone UE with non-continuous PRB allocation in the frequency domain maycause significant signal distortion and/or in-band/out-of-bandemissions. Furthermore, when multiplexing long PUSCH/PUCCH and shortPUSCH/PUCCH from different UEs or from the same UE, different schedulingfrequencies, such as mini-slot vs slot level scheduling and semi-staticvs dynamic scheduling, different HARQ processing timelines, anddifferent processing delays for UL transmission upon reception of ULgrant can be considered to determine UE behaviors.

According to a possible embodiment, a UE may operate according to thefollowing options to multiplex semi-statically configured shortPUCCH/PUSCH, such as for URLLC SR and grant-free UL data transmission,and dynamically scheduled long PUSCH/PUCCH, such as for grant-based ULdata transmission and aperiodic CSI report.

According to a possible option for UE operation, semi-static URLLC SR orgrant-free PUSCH resources may be UE-specifically or cell-specificallyconfigured. Even with UE-specific configuration, the time-frequencyresources may still be shared by multiple UEs, such as via CDM.

FIG. 4 is an example illustration 400 of multiplexing semi-staticallyconfigured short PUCCH with slot-based PUSCH from different UEsaccording to a possible embodiment. According to this option for UEoperation for multiplexing different UEs, UL DCI scheduling of longPUSCH/PUCCH can include an indication of the semi-statically configuredshort PUSCH/PUCCH resource for other UEs, such as UE 2, that fully orpartially overlaps with the long PUSCH/PUCCH resource in time and infrequency, such as for UE 1, as shown in the illustration 400. The UE,such as UE 1, can determine the overlapped Resource Elements (REs) basedon the indication and can perform rate-matching around the overlappedREs for the long PUSCH/PUCCH. If the semi-static short PUSCH/PUCCHresource is selected from a predefined set of resources, and/or theshort PUSCH/PUCCH resource is determined by combination of one ofpredefined configuration and a few configurable parameters, a signalingoverhead in UL DCI for indicating the semi-statically configured shortPUCCH/PUSCH resource can be reduced by including a selectedconfiguration index and a few configurable parameters.

FIG. 5 is an example illustration 500 of multiplexing semi-staticallyconfigured short PUCCH with slot-based PUSCH from one UE according to apossible embodiment. According to this option for UE operation formultiplexing within a single UE, if, in a given symbol, long PUCCH/PUSCHresource allocation includes or partially includes the semi-staticallyconfigured short PUCCH/PUSCH resources, the UE can consider theconfigured short PUCCH/PUSCH resources not available for longPUSCH/PUCCH and can perform rate-matching around the configured shortPUCCH/PUSCH resources. Although the UE may not transmit URLLC SR orgrant-free data transmission on the configured short PUCCH/PUSCHresources, other UEs may use the configured short PUCCH/PUSCH resources.Thus, the UE can perform rate-matching irrespective of whether itactually transmits short PUCCH/PUSCH on the configured resources. If, ina given symbol, long PUCCH/PUSCH resource allocation does not includethe semi-statically configured short PUCCH/PUSCH resources and if the UEis not capable of simultaneous transmissions on non-contiguous PRBs forexample, due to emission issues or UE capability, and the UE shouldtransmit short PUCCH/PUSCH, the short PUCCH/PUSCH transmission can bemoved into the allocated long PUCCH/PUSCH resource, as shown in theillustration 500. If the actual short PUCCH/PUSCH transmission from theUE may or may not occur, such as for URLLC SR or grant-freetransmission, and whether to transmit short PUCCH/PUSCH or not isdetermined in a mini-slot or non-slot level, where a mini-slot is atransmission duration smaller than a slot, it may be difficult for UE toperform rate-matching around the moved short PUCCH/PUSCH resources inadvance by taking into account the actual transmission. Thus, the UE maypuncture the long PUSCH/PUCCH for the moved short PUCCH/PUSCH resources,if short PUCCH(s)/PUSCH(s) are actually transmitted. In one examplewhere the long PUSCH/PUCCH has been prepared, such as by channel codingand rate-matching for the allocated long PUSCH/PUCCH resources, or is inthe process of being prepared for transmission prior to the need totransmit a short PUCCH/PUSCH transmission, such as from a trigger forURLLC SR or grant-free transmission, so to avoid the re-processing andthe associated processing delays and the need to reserve hardware timebudget for packet generation and preparation of the long PUSCH/PUCCH,the short PUSCH/PUCCH transmission can puncture the long PUSCH/PUCCHREs. In one example, the short PUSCH/PUCCH transmission can puncture atleast the overlapping long PUSCH/PUCCH symbols even if the shortPUSCH/PUCCH partially overlaps on some of the REs of the longPUSCH/PUCCH. Puncturing more than the just the overlapping symbols canbe done prior to and following the short PUSCH/PUCCH transmission toallow for power adjustment and setting settling time, as the targetedtransmission power for the short PUSCH/PUCCH and long PUSCH/PUCCH may bedifferent. In some examples, the long PUSCH/PUCCH can be dropped if theUE is unable or not capable of maintaining transmit phase continuityafter the short PUSCH/PUCCH transmission, such as due to a power change,a resource change, and/or power ramp-up/down transients. In someexamples, the long PUSCH/PUCCH may be resumed in the next mini-slot orslot in the case of mini-slot or slot aggregation allocating a pluralityof mini-slots or slots with each mini-slot or slot having its own phasereference signals. In another example, if the short PUSCH/PUCCH overlapsat least a portion of the reference signal symbols of the longPUSCH/PUCCH, the long PUSCH/PUCCH transmission can be dropped. In someexamples with intra-slot hopping, the long PUSCH/PUCCH transmission canbe dropped for the intra-slot hop dwell time. The long/PUSCHtransmission may be resumed starting at the start of the secondintra-slot hop dwell period if the long PUSCH/PUCCH transmission isdropped in the first hop dwell period. In another example, if the UE hasknowledge or is aware that the short PUSCH/PUCCH transmission is goingto overlap with an upcoming long PUSCH/PUCCH transmission, the UE candrop at least a significant portion if not all of the long PUSCH/PUCCHtransmission. In an example with multiple reference signals for longPUSCH/PUCCH in a slot and where the UE is assigned to use an orthogonalcover code over the two or reference signals, in the case of collisionbetween the short PUSCH/PUCCH with any portion of the reference signalswith Orthogonal Cover Code (OCC), at least a portion of the longPUSCH/PUCCH transmission can be dropped. This may correspond toOFDM/SC-FDMA symbols of the long PUSCH/PUCCH for which the referencesignals with OCC are a phase reference.

In another example, if a UE has semi-statically configured shortPUCCH/PUSCH, such as URLLC SR, resources and semi-statically configuredlong PUSCH/PUCCH, such as periodic CSI report, resources, if the shortPUCCH/PUSCH and long PUSCH/PUCCH resources occur on non-contiguous PRBsin the same slot, and if the UE does not support an UL transmission onnon-contiguous PRBs in the frequency domain, the UE may not use thesemi-statically configured short PUCCH/PUSCH resources, but the UE canmove short PUCCH/PUSCH transmissions within the long PUSCH/PUCCHresources. Furthermore, the UE can puncture the long PUSCH/PUCCH on theresource elements where short PUCCH(s)/PUSCH(s) are actuallytransmitted.

In one example, the UE can be configured with a semi-static resourcecorresponding to at least a portion of the short PUSCH/PUCCH torate-match around for a long PUSCH/PUCCH resource assignment if the longPUSCH/PUCCH resource allocation overlaps at least partially with thesemi-static configured resource. In this case, the semi-static resourcecan be as one or more resource blocks on one or more OFDM/SC-FDMAsymbols, where the number of OFDM/SC-FDMA symbols can be preferably muchsmaller than the number of OFDM/SC-FDMA symbols in the long PUSCH/PUCCH.In one example, rate-matching around for a long PUSCH/PUCCH resourceassignment can include rate-matching around the entire OFDM/SC-FDMAsymbols associated to the semi-static resource.

According to another possible embodiment, a NE can include an indicationon whether the UE has to monitor UE-specific or group-specific DCIcarrying dynamic puncturing information, which can be denoted as“puncturing DCI,” or not, such as via a 1-bit flag, in UL DCI schedulinglong PUSCH/PUCCH. Alternatively, the UE can monitor puncturing DCI ifthe number of allocated PRBs for long PUSCH/PUCCH is larger than acertain value. In UL DCI for long PUSCH/PUCCH, the NE can furtherindicate a monitoring interval of puncturing DCI, such as a slot-levelor mini-slot level interval.

FIG. 6 is an example illustration 600 of a puncturing pattern formini-slot or non-slot level monitoring of puncturing DCI within aslot-based PUSCH according to a possible embodiment. FIG. 7 is anexample illustration 700 of a puncturing pattern for slot levelmonitoring of puncturing DCI within a slot-based PUSCH according to apossible embodiment. The UE's dynamic puncturing on the long PUSCH/PUCCHmay be needed to multiplex dynamically scheduled short PUCCH/PUSCH forthe same UE or for different UE(s). To minimize the demodulationperformance degradation of the punctured long PUSCH/PUCCH, a NE mayallocate short PUCCH/PUSCH resources overlapped with the longPUSCH/PUCCH resource only in the long PUSCH/PUCCH with large PRBallocation. In one embodiment, the UE and the NE can derive puncturingpatterns and payload sizes for puncturing DCI based on the knowledge onthe allocated number of PRBs and symbols for long PUSCH/PUCCH and themonitoring interval of the puncturing DCI. This can limit signalingoverhead in the puncturing DCI and avoid increase of UE blind decodingcomplexity. In the example illustration 600, the UE can be signaled tomonitor puncturing DCI in every other symbol, such as mini-slot levelmonitoring, and applicability of puncturing on 2 possible locations ineach monitoring interval can be signaled with a 2-bit bitmap. In theillustration 700, the UE can be signaled to monitor puncturing DCI inevery slot and applicability of puncturing on 2 possible locations canalso be signaled with 2-bit bitmap.

FIG. 8 is an example flowchart 800 illustrating the operation of awireless communication device, such as the UE 110, according to apossible embodiment. At 810, a lack of a valid dedicated UL controlchannel resource configuration can be ascertained by the device. Thedevice identity can be a UE identity. The UL control channel can be aPUCCH or any other UL channel that can carry control signaling, such asChannel Quality Indicators (CQIs), Acknowledgement/NegativeAcknowledgements (ACK/NACKs), SRs, and other control signaling. Therecan be a lack of a valid dedicated UL control channel resource due tothe device not having a dedicated UL control channel resource, due tothe device having an expired dedicated UL control channel resourcebecause of UL timer expiration, due to release/reset of previouslyconfigured dedicated UL control channel resources, or due to any otherreason. According to a possible implementation, information of supportedUL control channel formats can be transmitted. According to anotherpossible implementation, two different types of UL channels, such asPUCCHs, in terms of transmission duration can be supported by thedevice. In different embodiments, the OFDM symbols can be OFDM symbols,DFT-s-OFDM symbols, and/or other symbols useful for a PUCCH. Accordingto a possible implementation, a RACH preamble can be transmitted. A RARmessage can be received in response to the transmitted RACH preamble.The RAR message can include information of an UL grant. The UL grant canbe a PUSCH grant or any other uplink channel grant. An UL message can betransmitted according the UL grant. The UL message can be a Msg3 messageor any other UL message. The UL message can carry at least a deviceidentity of the device. The DL message can be received in response totransmitting the UL message.

At 820, a number of symbols for an UL control channel can be determinedin response to ascertaining a lack of a valid dedicated UL controlchannel resource configuration. Determining can include determining thenumber of symbols based on a number of UL data channel transmissions fora same transport block and/or based on available UL symbols in a slotwhere the HARQ-ACK feedback to the DL message will be transmitted. TheUL data channel can be a PUSCH or any other UL data channel.

According to a possible implementation, an indication of a number ofsymbols for the UL control channel can be received via systeminformation. The indication can be an index to predefined set of ULcontrol channel configurations. The index can identify a number ofsymbols in a predefined set of numbers of symbols in the predefined setof UL control channel configurations. The indicated number of symbolscan be identified from the predefined set of numbers of symbols. Thepredetermined set of numbers of symbols can be based on a referencenumerology indicated in the system information. For example, differentnumerologies provide for different subcarrier spacing in the frequencydomain, where slot duration can get shorter as the subcarrier spacinggets wider. Determining can include determining the number of symbolsbased on the received indication.

At 830, a DL message can be received. The DL message can be based on adevice identity of the device. The DL message can be a Msg4 message orany other message. At 840, a HARQ-ACK feedback on the UL control channelcan be transmitted using the determined number of symbols in response toreceiving the DL message. The index received in the indication above canalso identify a cell-specific PRB offset for the UL control channel andthe HARQ-ACK feedback can be transmitted on the UL control channel, inresponse to receiving the DL message, using the identified cell-specificPRB offset.

The index can additionally identify a starting symbol for the UL controlchannel and the HARQ-ACK feedback on the UL control channel can betransmitted using the identified starting symbol in response toreceiving the DL message. For example, for PUCCH longer than twosymbols, an allocated PRB index, where PRB indexing starts from abandwidth part boundary, can be determined based on a dynamicallysignaled value together with a semi-statically indicated, such as viaRAR or SIB, PRB offset. The DL message can be based on an identity ofthe device by including the device identity, by scrambling the messageusing the device identity, by being addressed by the device identity, orotherwise based on the device identity. Transmitting the HARQ-ACKfeedback can include transmitting a HARQ-ACK feedback via a long PUCCHin response to receiving the DL message.

According to a possible implementation, DL scheduling DCI can bereceived. The DL scheduling DCI can include information of adevice-specific PRB offset and cyclic shift information of a basesequence for the HARQ-ACK feedback transmission. The HARQ-ACK can use aparticular cyclic shift and the HARQ-NACK can use a different cyclicshift. A base sequence for ACK/NACK transmission, such as the HARQ-ACKfeedback, can be identified via cell-specific information, such as acell-specific scrambling ID parameter, a ‘hoppingID’, and/or othercell-specific information. The cyclic shift information can furtheridentify the device-specific cyclic shift of the base sequence that thedevice should use for its ACK/NACK transmission.

FIG. 9 is an example flowchart 900 illustrating the operation of awireless communication device, such as the NE 120, according to apossible embodiment. At 910, a number of symbols for an UL controlchannel can be determined by a device, such as the NE 120. The number ofsymbols for the UL control channel can be determined based on cell size.The number of symbols for the UL control channel can also be determinedbased on number of configured symbols for a DL control resource. Thenumber of symbols can additionally be determined based on a number ofPUSCH transmissions for a same transport block and/or based on availableUL symbols in a slot where the HARQ-ACK feedback to the DL message willbe transmitted.

At 920, system information indicating the number of symbols for the ULcontrol channel can be transmitted. An indication of a number of symbolsfor subsequent UL control channel transmissions can also be transmitted.The number of symbols for subsequent UL control channel transmissionscan be based on a UE's PHR and/or an average number of UL transmissionsfor successful decoding of one UL TB. The indication can be an index topredefined set of UL control channel configurations. The index can alsoidentify a number of symbols in a predefined set of numbers of symbolsin the predefined set of UL control channel configurations. Thepredetermined set of numbers of symbols can be based on a referencenumerology indicated in the system information.

At 930, a DL message based on a device identity can be transmitted. Thedevice identity can be a UE ID or any other device identity. DLscheduling DCI can also be transmitted. The DL scheduling DCI caninclude information of a device-specific PRB offset and cyclic shiftinformation of a base sequence for the HARQ-ACK feedback.

According to a possible implementation, a RACH preamble can be received.A RAR message can be transmitted in response to the received RACHpreamble. The RAR message can include information of an UL grant. The ULgrant can be a PUSCH grant. An UL message can be received according theUL grant. The UL message can carry at least a device identity of adevice. The DL message can then be transmitted at 930 in response toreceiving the UL message.

At 940, a HARQ-ACK feedback transmission can be received on the ULcontrol channel using the indicated number of symbols in response totransmitting the DL message. According to a possible implementation, theindex described above can also identify a cell-specific PRB offset forthe UL control channel and the HARQ-ACK feedback can be received on theUL control channel using the identified cell-specific PRB offset inresponse to transmitting the DL message. The index can further identifya starting symbol for the UL control channel and the HARQ-ACK feedbackcan be received on the UL control channel using the identified startingsymbol in response to transmitting the DL message.

FIG. 10 is an example flowchart 1000 illustrating the operation of awireless communication device, such as the UE 110, according to apossible embodiment. At 1010, semi-static configuration information fora short physical UL channel resource can be received at a device. Theshort physical UL channel resource can correspond to a short physical ULchannel A physical uplink channel can be a PUCCH, a PUSCH, or any otherphysical uplink channel. The short physical UL channel resource can beshared by multiple devices. For example, the short physical UL channelresource can be shared by multiple UEs via Code Division Multiplexing(CDM).

At 1020, scheduling information to transmit over a long physical ULchannel resource corresponding to a long physical UL channel can bereceived. The long physical UL channel resource and the short physicalUL channel resource can at least partially overlap in time. The shortphysical UL channel resource can include contiguous physical resourceblocks in frequency and contiguous OFDM or SC-FDMA symbols in time. Thelong physical UL channel resource can include contiguous physicalresource blocks in frequency and contiguous OFDM or SC-FDMA symbols intime. The long physical UL channel can be longer in duration than theshort physical UL channel.

According to a possible implementation the short physical UL channelresource can be determined to partially overlap the long physical ULchannel in the frequency domain. The short physical UL channel resourcecan be modified to fully overlap with the long physical UL channelresource in the frequency domain based on determining the short physicalUL channel resource partially overlaps the long physical UL channel inthe frequency domain. The modification can ensure no change of powerspectral density.

At 1030, transmission can be made over the long physical UL channelresource if the device does not support an UL transmission on one ormore non-contiguous PRBs in the frequency domain. According to apossible implementation rate-matching of the long physical UL channelaround the short physical UL channel resource can be performed if thelong physical UL channel resource for the long physical UL channel atleast partially includes the short physical UL channel resource in thefrequency domain. Rate-matching of the long physical UL channel aroundthe modified short physical UL channel resource can be performed if thelong physical UL channel resource for the long physical UL channel atleast partially includes the short physical UL channel resource in thefrequency domain.

According to a possible implementation, a URLLC SR can be transmitted onthe short physical UL channel resource. The URLLC SR can also betransmitted on the modified short physical UL channel resource.

According to another possible implementation, a grant-free UL datatransmission can be performed on the short physical UL channel resource.The grant-free UL data transmission can also be performed on themodified short physical UL channel resource.

According to another possible implementation, a physical UL channelresource can be identified in the long physical UL channel resource totransmit the short physical UL channel if the long physical UL channelresource does not overlap the short physical UL channel resource in thefrequency domain. The physical UL channel resource can be fully, such ascompletely, within the long physical UL channel resource.

According to another possible implementation, the short physical ULchannel can be transmitted on the identified physical UL channelresource. The long physical UL channel can be punctured on theidentified short physical UL channel resource. The long physical ULchannel can be punctured on the identified short physical UL channelresource and additional resource elements. This can allow for poweradjustment and setting settling time. Transmission of the long physicalUL channel can be skipped after transmitting the short physical ULchannel if transmit phase continuity cannot be maintained aftertransmitting the short physical UL channel. For example, thetransmission of the long physical UL channel can be dropped aftertransmitting the short physical UL channel, if transmit phase continuitycannot be maintained after transmitting the short physical UL channel.

FIG. 11 is an example flowchart 1100 illustrating the operation of awireless communication device, such as the NE 120, according to apossible embodiment. At 1110, semi-static configuration information canbe ascertained for a short physical UL channel resource corresponding toa short physical UL channel A physical UL channel can be a PUCCH, aPUSCH, or any other physical UL channel. The short physical UL channelresource can be shared by multiple devices. At 1120, the semi-staticconfiguration information for the short physical UL channel resource canbe transmitted.

At 1130, scheduling information to transmit over a long physical ULchannel resource corresponding to a long physical UL channel can bedetermined. The long physical UL channel and the short physical ULchannel resource can at least partially overlap in time. The longphysical UL channel can be longer in duration than the short physical ULchannel. At 1140, the determined scheduling information can betransmitted.

At 1150, information can be received on the long physical UL channelresource. The long physical UL channel can be received rate-matchedaround the short physical UL channel resource if the long physical ULchannel resource at least partially includes the short physical ULchannel resource in the frequency domain. An URLLC SR can also bereceived on the short physical UL channel resource.

According to a possible implementation, a physical UL channel resourcein the long physical UL channel resource can be identified to receivethe short physical UL channel if the long physical UL channel resourcedoes not overlap the short physical UL channel resource in the frequencydomain. The physical UL channel resource can be fully, such ascompletely, within the long physical UL channel resource. The shortphysical UL channel can be received on the identified physical ULchannel resource. Receiving the short physical UL channel can includedetecting transmission of the short physical UL channel on theidentified physical UL channel resource. The long physical UL channelcan be received punctured on the identified short physical UL channelresource. The long physical UL channel can be received punctured on theidentified short physical UL channel resource and additional resourceelements. Transmission of the long physical UL channel aftertransmitting the short physical UL channel can be skipped if transmitphase continuity cannot be maintained after transmitting the shortphysical UL channel.

FIG. 12 is an example flowchart 1200 illustrating the operation of awireless communication device, such as the UE 110, according to apossible embodiment. At 1210, scheduling information to transmit aphysical UL channel can be received. The scheduling information caninclude modification information regarding modifying a physical ULchannel transmission. For example, the scheduling information caninclude the modification information if a number of PRBs allocated forthe physical UL channel is larger than a threshold number of PRBs. Thescheduling information can also include information regarding at leastone allocated PRB and at least one allocated symbol for the physical ULchannel. The scheduling information can be in DCI. The DCI includingscheduling information can be different from DCI including dynamicpuncturing information. The modification information can include anindication of rate-matching of a physical UL channel around REs. Themodification information can also include an identification of the REsaround which to perform rate-matching. The modification information canbe included in the scheduling information if a number of PRBs allocatedfor the physical UL channel is larger than a threshold number of PRBs.The modification information can additionally include informationregarding monitoring for DCI including dynamic puncturing information.The modification information can further include information regardingmonitoring a PDCCH for the DCI including dynamic puncturing information.

At 1220, the physical UL channel can be transmitted based on thescheduling information including the modification information.Transmitting can include performing rate-matching of the physical ULchannel around REs based on the indication of rate matching.Transmitting can also include performing rate-matching of the physicalUL channel around the REs around which to perform rate-matching. The REsaround which to perform rate-matching can be determined based on a setof resources determined by a predefined configuration and/or aconfigurable parameter. For example, the predefined configuration can bea set of rate matching or puncturing resource grids and the configurableparameter can be a granularity of rate matching or puncturing resourcegrid.

According to a possible implementation, an indication of a monitoringinterval for a PDCCH carrying the DCI including the dynamic puncturinginformation can be received. A puncturing pattern and a payload size ofthe DCI including the dynamic puncturing information can be determined.The puncturing pattern and the payload size can be determined based onthe scheduling information for the physical UL channel and themonitoring interval. Monitoring occasions can be determined based on theindicated monitoring interval. The monitoring occasions can occur afterreceiving the scheduling information to transmit the physical UL channeland before completing transmission of the physical UL channel. The DCIincluding the dynamic puncturing information can be monitored for.Monitoring can include monitoring for a PDCCH carrying the DCI includingdynamic puncturing information based on the determined monitoringoccasions. The DCI including the dynamic puncturing information can bedecoded. A resource for puncturing can be determined based on thedynamic puncturing information. The physical UL channel can be puncturedon the determined resource for puncturing. Transmitting at 1220 caninclude transmitting the punctured physical UL channel.

FIG. 13 is an example flowchart 1300 illustrating the operation of awireless communication device, such as the NE 120, according to apossible embodiment. At 1310, scheduling information to transmit aphysical UL channel can be determined. The scheduling information caninclude modification information regarding modifying a physical ULchannel transmission. The scheduling information can also includeinformation regarding at least one allocated PRB and at least oneallocated symbol for the physical UL channel. The modificationinformation can include information regarding monitoring a PDCCH for DCIincluding dynamic puncturing information if a number of PRBs allocatedfor the physical UL channel is larger than a threshold number of PRBs.The modification information can be included in the schedulinginformation if a number of PRBs allocated for the physical UL channel islarger than a threshold number of PRBs.

According to a possible implementation, an indication of rate-matchingof a physical UL channel around REs can be determined and themodification information can include the indication of rate-matching ofa physical UL channel around REs. Also, REs around which to performrate-matching can be identified and the modification information caninclude an identification of the REs around which to performrate-matching. The REs around which to perform rate-matching can bedetermined based on a set of resources determined by a predefinedconfiguration and/or a configurable parameter.

At 1320, the scheduling information including the modificationinformation can be transmitted. At 1330, the physical UL channel can bereceived based on the scheduling information including the modificationinformation.

According to a possible implementation, the modification information caninclude information regarding monitoring for DCI including dynamicpuncturing information. The modification information can also includeinformation regarding monitoring a PDCCH for the DCI including dynamicpuncturing information. The DCI including dynamic puncturing informationcan be transmitted. An indication of a monitoring interval for a PDCCHcarrying the DCI including the dynamic puncturing information can betransmitted. Monitoring occasions can be determined based on theindicated monitoring interval. The monitoring occasions can occur aftertransmitting the scheduling information to transmit the physical ULchannel and before completing reception of the physical UL channelTransmitting the DCI can include transmitting a PDCCH carrying the DCIincluding dynamic puncturing information based on the indicatedmonitoring interval. A puncturing pattern and a payload size of the DCIincluding the dynamic puncturing information can be determined. Thepuncturing pattern and the payload size can be determined based on thescheduling information for the physical UL channel and the monitoringinterval. The received physical UL channel can be punctured based on thedynamic puncturing information.

It should be understood that, notwithstanding the particular steps asshown in the figures, a variety of additional or different steps can beperformed depending upon the embodiment, and one or more of theparticular steps can be rearranged, repeated or eliminated entirelydepending upon the embodiment. Also, some of the steps performed can berepeated on an ongoing or continuous basis simultaneously while othersteps are performed. Furthermore, different steps can be performed bydifferent elements or in a single element of the disclosed embodiments.

FIG. 14 is an example block diagram of an apparatus 1400, such as the UE110, the network entity 120, or any other wireless communication devicedisclosed herein, according to a possible embodiment. The apparatus 1400can include a housing 1410, a controller 1420 coupled to the housing1410, audio input and output circuitry 1430 coupled to the controller1420, a display 1440 coupled to the controller 1420, a transceiver 1470coupled to the controller 1420, at least one antenna 1475 coupled to thetransceiver 1470, a user interface 1460 coupled to the controller 1420,a memory 1450 coupled to the controller 1420, and a network interface1480 coupled to the controller 1420. The apparatus 1400 may notnecessarily include all of the illustrated elements for differentembodiments of the present disclosure. The apparatus 1400 can performthe methods described in all the embodiments.

The display 1440 can be a viewfinder, a Liquid Crystal Display (LCD), aLight Emitting Diode (LED) display, an Organic Light Emitting Diode(OLED) display, a plasma display, a projection display, a touch screen,or any other device that displays information. The transceiver 1470 canbe one or more transceivers that can include a transmitter and/or areceiver. The audio input and output circuitry 1430 can include amicrophone, a speaker, a transducer, or any other audio input and outputcircuitry. The user interface 1460 can include a keypad, a keyboard,buttons, a touch pad, a joystick, a touch screen display, anotheradditional display, or any other device useful for providing aninterface between a user and an electronic device. The network interface1480 can be a Universal Serial Bus (USB) port, an Ethernet port, aninfrared transmitter/receiver, an IEEE 1394 port, a wirelesstransceiver, a WLAN transceiver, or any other interface that can connectan apparatus to a network, device, and/or computer and that can transmitand receive data communication signals. The memory 1450 can include aRandom Access Memory (RAM), a Read Only Memory (RON), an optical memory,a solid state memory, a flash memory, a removable memory, a hard drive,a cache, or any other memory that can be coupled to an apparatus.

The apparatus 1400 or the controller 1420 may implement any operatingsystem, such as Microsoft Windows®, UNIX®, or LINUX®, Android™, or anyother operating system. Apparatus operation software may be written inany programming language, such as C, C++, Java or Visual Basic, forexample. Apparatus software may also run on an application framework,such as, for example, a Java® framework, a .NET® framework, or any otherapplication framework. The software and/or the operating system may bestored in the memory 1450 or elsewhere on the apparatus 1400. Theapparatus 1400 or the controller 1420 may also use hardware to implementdisclosed operations. For example, the controller 1420 may be anyprogrammable processor. Disclosed embodiments may also be implemented ona general-purpose or a special purpose computer, a programmedmicroprocessor or microprocessor, peripheral integrated circuitelements, an application-specific integrated circuit or other integratedcircuits, hardware/electronic logic circuits, such as a discrete elementcircuit, a programmable logic device, such as a programmable logicarray, field programmable gate-array, or the like. In general, thecontroller 1420 may be any controller or processor device or devicescapable of operating an apparatus and implementing the disclosedembodiments. Some or all of the additional elements of the apparatus1400 can also perform some or all of the operations of the disclosedembodiments.

According to a possible embodiment in operation as a UE, the controller1420 can ascertain a lack of a valid dedicated UL control channelresource configuration. The controller 1420 can determine a number ofsymbols for an UL control channel in response to ascertaining a lack ofa valid dedicated UL control channel resource configuration. Determiningcan include determining the number of symbols based on a number of ULdata channel transmissions for a same transport block and/or based onavailable UL symbols in a slot where the HARQ-ACK feedback to the DLmessage will be transmitted.

According to a possible implementation, the transceiver 1470 canreceive, via system information, an indication of a number of symbolsfor the UL control channel and the controller 1420 can determine thenumber of symbols based on the received indication. The indication canbe an index to predefined set of UL control channel configurations.According to a possible implementation, the index can identify a numberof symbols in a predefined set of numbers of symbols in the predefinedset of UL control channel configurations and the controller 1470 canidentify the indicated number of symbols from the predefined set ofnumbers of symbols. The predetermined set of numbers of symbols can bebased on a reference numerology indicated in the system information.

The transceiver 1470 can receive a DL message. The DL message can bebased on a device identity of the device. The transceiver 1470 can alsoreceive DL scheduling DCI, where the DL scheduling DCI includesinformation of a device-specific PRB offset and cyclic shift informationof a base sequence for the HARQ-ACK feedback transmission.

The transceiver 1470 can transmit, in response to receiving the DLmessage, a HARQ-ACK feedback on the UL control channel using thedetermined number of symbols. According to a possible implementation,the index can further identify a cell-specific PRB offset for the ULcontrol channel and the transceiver 1470 can transmit, in response toreceiving the DL message, the HARQ-ACK feedback on the UL controlchannel using the identified cell-specific PRB offset. According to apossible implementation, the index can also identify a starting symbolfor the UL control channel and the transceiver 1470 can transmit, inresponse to receiving the DL message, the HARQ-ACK feedback on the ULcontrol channel using the identified starting symbol.

According to a possible embodiment in operation as a NE, the controller1420 can determine a number of symbols for an UL control channelAccording to a possible implementation, the controller 1420 candetermine the number of symbols based on a number of PUSCH transmissionsfor a same transport block and/or based on available UL symbols in aslot where the HARQ-ACK feedback to the DL message will be transmitted.The transceiver 1470 can transmit system information indicating thenumber of symbols for the UL control channel. The number of symbols forthe UL control channel can be determined based on cell size. The numberof symbols for the UL control channel can also be determined based onnumber of configured symbols for a DL control resource. The transceiver1470 can transmit a DL message based on a device identity, such as anidentity of the device the DL message is being transmitted to. Thetransceiver 1470 can transmit DL scheduling DCI. The DL scheduling DCIcan include information of a device-specific PRB offset and cyclic shiftinformation of a base sequence for HARQ-ACK feedback transmission. Thetransceiver 1470 can receive, in response to transmitting the DLmessage, a HARQ-ACK feedback on the UL control channel using theindicated number of symbols.

According to a possible implementation, the transceiver 1470 can receivea RACH preamble. The transceiver 1470 can transmit a RAR message inresponse to the received RACH preamble. The RAR message can includeinformation of an UL grant. The transceiver 1470 can receive an ULmessage according the UL grant. The UL message can carry at least adevice identity of a device that sent the UL message.

According to another possible implementation, the transceiver 1470 cantransmit an indication of a number of symbols for subsequent UL controlchannel transmissions. The number of symbols for subsequent UL controlchannel transmissions can be based on a UE's PHR and/or an averagenumber of UL transmissions for successful decoding of one UL TB.

According to a possible embodiment in operation as a UE, the controller1420 can control operations of the apparatus 1400. The transceiver 1470can receive semi-static configuration information for a short physicalUL channel resource corresponding to a short physical UL channel. Theshort physical UL channel resource can be shared by multiple devices,such as multiple UEs.

The transceiver 1470 can receive scheduling information to transmit overa long physical UL channel resource corresponding to a long physical ULchannel. The long physical UL channel resource and the short physical ULchannel resource can at least partially overlap in time. The longphysical UL channel can be longer in duration than the short physical ULchannel.

The transceiver 1470 can transmit over the long physical UL channelresource if the device does not support an UL transmission on one ormore non-contiguous PRBs in the frequency domain. The controller 1420can perform rate-matching of the long physical UL channel around theshort physical UL channel resource for transmission of the long physicalUL channel if the long physical UL channel resource for the longphysical UL channel at least partially includes the short physical ULchannel resource in the frequency domain. The transceiver 1470 can alsotransmit a URLLC SR on the short physical UL channel resource. Thetransceiver 1470 can further perform a grant-free UL data transmissionon the short physical UL channel resource.

According to a possible implementation, the controller 1420 candetermine that the short physical UL channel resource partially overlapsthe long physical UL channel in the frequency domain. The controller1420 can modify the short physical UL channel resource to fully overlapwith the long physical UL channel resource in the frequency domain basedon determining the short physical UL channel resource partially overlapsthe long physical UL channel in the frequency domain. The controller1420 can perform rate-matching of the long physical UL channel aroundthe modified short physical UL channel resource if the long physical ULchannel resource for the long physical UL channel at least partiallyincludes the short physical UL channel resource in the frequency domain.

According to another possible implementation, the controller 1420 canidentify a physical UL channel resource in the long physical UL channelresource to transmit the short physical UL channel if the long physicalUL channel resource does not overlap the short physical UL channelresource in the frequency domain. The transceiver 1470 can transmit theshort physical UL channel on the identified physical UL channelresource. The controller 1420 can puncture the long physical UL channelon the identified short physical UL channel resource.

According to a possible embodiment in operation as a NE, the controller1420 can ascertain semi-static configuration information for a shortphysical UL channel resource corresponding to a short physical ULchannel. The short physical UL channel resource can be shared bymultiple devices. The transceiver 1470 can transmit the semi-staticconfiguration information for the short physical UL channel resource.The controller 1420 can determine scheduling information to transmitover a long physical UL channel resource corresponding to a longphysical UL channel. The long physical UL channel and the short physicalUL channel resource can at least partially overlap in time. The longphysical UL channel can be longer in duration than the short physical ULchannel. The transceiver 1470 can transmit the determined schedulinginformation. The transceiver 1470 can receive information on the longphysical UL channel resource. The transceiver 1470 can receive the longphysical UL channel rate-matched around the short physical UL channelresource if the long physical UL channel resource at least partiallyincludes the short physical UL channel resource in the frequency domain.The transceiver 1470 can also receiver an URLLC SR on the short physicalUL channel resource.

According to a possible implementation, the controller 1420 can identifya physical UL channel resource in the long physical UL channel resourceto receive the short physical UL channel if the long physical UL channelresource does not overlap the short physical UL channel resource in thefrequency domain. The transceiver 1470 can receive the short physical ULchannel on the identified physical UL channel resource. Receiving theshort physical UL channel can include detecting transmission of theshort physical UL channel on the identified physical UL channelresource. The transceiver 1470 can receive the long physical UL channelpunctured on the identified short physical UL channel resource. Thetransceiver 1470 can receive the long physical UL channel punctured onthe identified short physical UL channel resource and additionalresource elements. Transmission of the long physical UL channel aftertransmitting the short physical UL channel can be skipped if transmitphase continuity cannot be maintained after transmitting the shortphysical UL channel.

According to a possible embodiment in operation as a UE, the controller1420 can control operations of the apparatus 1400. The transceiver 1470can receive scheduling information to transmit a physical UL channel.The scheduling information can include modification informationregarding modifying a physical UL channel transmission. The schedulinginformation can also include information regarding at least oneallocated PRB and at least one allocated symbol for the physical ULchannel. The modification information can include an indication ofrate-matching of a physical UL channel around REs. The modificationinformation can also include an identification of the REs around whichto perform rate-matching. The modification information can be includedin the scheduling information if a number of PRBs allocated for thephysical UL channel is larger than a threshold number of PRBs. Thecontroller 1420 can determine the REs around which to performrate-matching based on a set of resources determined by a predefinedconfiguration and/or a configurable parameter.

The transceiver 1470 can transmit the physical UL channel based on thescheduling information including the modification information.Transmitting can include performing rate-matching of the physical ULchannel around REs based on the indication of rate matching.Transmitting can also include performing rate-matching of the physicalUL channel around the REs around which to perform rate-matching.

According to a possible implementation, the modification information caninclude information regarding monitoring for DCI including dynamicpuncturing information. The modification information can also includeinformation regarding monitoring a PDCCH for the DCI including dynamicpuncturing information. The transceiver 1470 can receive an indicationof a monitoring interval for a PDCCH carrying the DCI including thedynamic puncturing information. The controller 1420 can determinemonitoring occasions based on the indicated monitoring interval. Thecontroller 1420 can monitor for the DCI including the dynamic puncturinginformation. Monitoring for the DCI can include monitoring for a PDCCHcarrying the DCI including dynamic puncturing information based on thedetermined monitoring occasions. The monitoring occasions can occurafter receiving the scheduling information to transmit the physicaluplink channel and before completing transmission of the physical uplinkchannel. The controller 1420 can decode the DCI including the dynamicpuncturing information. The controller 1420 can determine a resource forpuncturing based on the dynamic puncturing information. The controller1420 can determine a puncturing pattern and a payload size of the DCIincluding the dynamic puncturing information based on the schedulinginformation for the physical uplink channel and the monitoring interval.The controller 1420 can puncture the physical UL channel on thedetermined resource for puncturing. The transceiver 1470 can transmitthe physical UL channel by transmitting the punctured physical ULchannel.

According to a possible embodiment in operation as a NE, the controller1420 can determine scheduling information to transmit a physical ULchannel. The scheduling information including modification informationcan regard modifying a physical UL channel transmission. The schedulinginformation can also include information regarding at least oneallocated PRB and at least one allocated symbol for the physical ULchannel. The modification information can include information regardingmonitoring a PDCCH for DCI including dynamic puncturing information if anumber of PRBs allocated for the physical UL channel is larger than athreshold number of PRBs. The controller 1420 can also determine anindication of rate-matching of a physical UL channel around REs and themodification information can include the indication of rate-matching ofa physical UL channel around REs. The controller 1420 can also identifyREs around which to perform rate-matching and the modificationinformation can include an identification of the REs around which toperform rate-matching. The controller 1420 can determine the REs aroundwhich to perform rate-matching based on a set of resources determined byat least one selected from a predefined configuration and a configurableparameter. The modification information can also include informationregarding monitoring for DCI including dynamic puncturing information.The modification information can be included in the schedulinginformation if a number of PRBs allocated for the physical UL channel islarger than a threshold number of PRBs. The DCI including the dynamicpuncturing information can be transmitted after transmitting thescheduling information for the physical uplink channel and beforecompleting reception of the physical uplink channel. A puncturingpattern and a payload size of the DCI including the dynamic puncturinginformation can be based on the scheduling information for the physicaluplink channel and a monitoring interval for the DCI including thedynamic puncturing information.

The transceiver 1470 can transmit the scheduling information includingthe modification information. The transceiver 1470 can also transmit theDCI including dynamic puncturing information. The transceiver 1470 canreceive the physical UL channel based on the scheduling informationincluding the modification information. The received physical UL channelcan be punctured based on the dynamic puncturing information.

The method of this disclosure can be implemented on a programmedprocessor. However, the controllers, flowcharts, and modules may also beimplemented on a general purpose or special purpose computer, aprogrammed microprocessor or microcontroller and peripheral integratedcircuit elements, an integrated circuit, a hardware electronic or logiccircuit such as a discrete element circuit, a programmable logic device,or the like. In general, any device on which resides a finite statemachine capable of implementing the flowcharts shown in the figures maybe used to implement the processor functions of this disclosure.

While this disclosure has been described with specific embodimentsthereof, it is evident that many alternatives, modifications, andvariations will be apparent to those skilled in the art. For example,various components of the embodiments may be interchanged, added, orsubstituted in the other embodiments. Also, all of the elements of eachfigure are not necessary for operation of the disclosed embodiments. Forexample, one of ordinary skill in the art of the disclosed embodimentswould be enabled to make and use the teachings of the disclosure bysimply employing the elements of the independent claims. Accordingly,embodiments of the disclosure as set forth herein are intended to beillustrative, not limiting. Various changes may be made withoutdeparting from the spirit and scope of the disclosure.

In this document, relational terms such as “first,” “second,” and thelike may be used solely to distinguish one entity or action from anotherentity or action without necessarily requiring or implying any actualsuch relationship or order between such entities or actions. The phrase“at least one of,” “at least one selected from the group of,” or “atleast one selected from” followed by a list is defined to mean one,some, or all, but not necessarily all of, the elements in the list. Theterms “comprises,” “comprising,” “including,” or any other variationthereof, are intended to cover a non-exclusive inclusion, such that aprocess, method, article, or apparatus that comprises a list of elementsdoes not include only those elements but may include other elements notexpressly listed or inherent to such process, method, article, orapparatus. An element proceeded by “a,” “an,” or the like does not,without more constraints, preclude the existence of additional identicalelements in the process, method, article, or apparatus that comprisesthe element. Also, the term “another” is defined as at least a second ormore. The terms “including,” “having,” and the like, as used herein, aredefined as “comprising.” Furthermore, the background section is writtenas the inventor's own understanding of the context of some embodimentsat the time of filing and includes the inventor's own recognition of anyproblems with existing technologies and/or problems experienced in theinventor's own work.

We claim:
 1. A method comprising: receiving, at a device, a semi-staticconfiguration information for a short physical uplink channel resourcecorresponding to a short physical uplink channel; receiving schedulinginformation to transmit over a long physical uplink channel resourcecorresponding to a long physical uplink channel, where the long physicaluplink channel resource and the short physical uplink channel resourceat least partially overlap in time, and where the long physical uplinkchannel is longer in duration than the short physical uplink channel;performing rate-matching of the long physical uplink channel around theshort physical uplink channel resource if the long physical uplinkchannel resource at least partially includes the short physical uplinkchannel resource in the frequency domain, where the rate-matching isperformed irrespective of whether there is data for transmission on theshort physical uplink channel resource; and transmitting therate-matched long physical uplink channel when there is no transmissionof the short physical uplink channel from the device.
 2. The methodaccording to claim 1, further comprising: determining that the shortphysical uplink channel resource partially overlaps the long physicaluplink channel in the frequency domain and there is a transmission ofthe short physical uplink channel from the device; modifying the shortphysical uplink channel resource to fully overlap with the long physicaluplink channel resource in the frequency domain based on determining theshort physical uplink channel resource partially overlaps the longphysical uplink channel in the frequency domain and there is thetransmission of the short physical uplink channel from the device; andtransmitting the short physical uplink channel on the modified shortphysical uplink channel resource.
 3. The method according to claim 2,further comprising performing rate-matching of the long physical uplinkchannel around the modified short physical uplink channel resource ifthe long physical uplink channel resource for the long physical uplinkchannel at least partially includes the short physical uplink channelresource in the frequency domain.
 4. The method according to claim 1,wherein the short physical uplink channel resource is shared by multipledevices.
 5. The method according to claim 1, wherein the short physicaluplink channel is a physical uplink control channel configured for anultra-reliable low-latency communication scheduling request, and themethod further comprises transmitting the ultra-reliable low-latencycommunication scheduling request on the short physical uplink channelresource.
 6. The method according to claim 1, wherein the short physicaluplink channel is a grant-free physical uplink shared channel, and themethod further comprises performing the grant-free uplink datatransmission on the short physical uplink channel resource.
 7. Themethod according to claim 1, further comprising identifying a physicaluplink channel resource in the long physical uplink channel resource totransmit the short physical uplink channel if the long physical uplinkchannel resource does not overlap the short physical uplink channelresource in the frequency domain and there is a transmission of theshort physical uplink channel from the device.
 8. The method accordingto claim 7, further comprising: transmitting the short physical uplinkchannel on the identified physical uplink channel resource; andpuncturing the long physical uplink channel on the identified shortphysical uplink channel resource.
 9. The method according to claim 8,further comprising puncturing the long physical uplink channel on theidentified short physical uplink channel resource and additionalresource elements.
 10. The method according to claim 9, furthercomprising skipping transmission of the long physical uplink channelafter transmitting the short physical uplink channel, if transmit phasecontinuity cannot be maintained after transmitting the short physicaluplink channel.
 11. An apparatus comprising: a controller configured tocontrol operations of the apparatus; and a transceiver coupled to thecontroller, where the transceiver receives semi-static configurationinformation for a short physical uplink channel resource correspondingto a short physical uplink channel, receives scheduling information totransmit over a long physical uplink channel resource corresponding to along physical uplink channel, where the long physical uplink channelresource and the short physical uplink channel resource at leastpartially overlap in time, and where the long physical uplink channel islonger in duration than the short physical uplink channel, performsrate-matching of the long physical uplink channel around the shortphysical uplink channel resource if the long physical uplink channelresource at least partially includes the short physical uplink channelresource in the frequency domain, where the rate-matching is performedirrespective of whether there is data for transmission on the shortphysical uplink channel resource, and transmits the rate-matched longphysical uplink channel when there is no transmission of the shortphysical uplink channel from the device.
 12. The apparatus according toclaim 11, wherein the controller determines that the short physicaluplink channel resource partially overlaps the long physical uplinkchannel in the frequency domain and there is a transmission of the shortphysical uplink channel from the apparatus, modifies the short physicaluplink channel resource to fully overlap with the long physical uplinkchannel resource in the frequency domain based on determining the shortphysical uplink channel resource partially overlaps the long physicaluplink channel in the frequency domain and there is the transmission ofthe short physical uplink channel from the device, and transmits theshort physical uplink channel on the modified short physical uplinkchannel resource.
 13. The apparatus according to claim 12, wherein thecontroller performs rate-matching of the long physical uplink channelaround the modified short physical uplink channel resource if the longphysical uplink channel resource for the long physical uplink channel atleast partially includes the short physical uplink channel resource inthe frequency domain.
 14. The apparatus according to claim 11, whereinthe short physical uplink channel resource is shared by multipledevices.
 15. The apparatus according to claim 11, wherein the shortphysical uplink channel is a physical uplink control channel configuredfor an ultra-reliable low-latency communication scheduling request, andwherein the transceiver transmits the ultra-reliable low-latencycommunication scheduling request on the short physical uplink channelresource.
 16. The apparatus according to claim 11, wherein the shortphysical uplink channel is a grant-free physical uplink shared channel,and wherein the transceiver performs a grant-free uplink datatransmission on the short physical uplink channel resource.
 17. Theapparatus according to claim 11, wherein the controller identifies aphysical uplink channel resource in the long physical uplink channelresource to transmit the short physical uplink channel if the longphysical uplink channel resource does not overlap the short physicaluplink channel resource in the frequency domain and there is atransmission of the short physical uplink channel from the apparatus.18. The apparatus according to claim 17, wherein the transceivertransmits the short physical uplink channel on the identified physicaluplink channel resource, and wherein the controller punctures the longphysical uplink channel on the identified short physical uplink channelresource.